A Study of 28 Peering Policies
The following are snippets of Peering Policy Clauses found in the Peering Rules of the Road - A Study of 28 Peering Policies study. Clauses were categorized and put into rough categories for comparison.
The following are snippets of Peering Policy Clauses found in the Peering Rules of the Road - A Study of 28 Peering Policies study. Clauses were categorized and put into rough categories for comparison.
Use of the Internet Routing Registry (IRR) is strongly encouraged for prompt prefix filter updates. Networks that do not provide a Routing Registry object to use for filter generation may have all routes filtered based upon some arbitrary criteria, such as mask length, or number of prefixes announced. – Speakeasy
Speakeasy maintains the right to add an entry describing any peering interconnect into the Internet Routing Registry system for the purpose of easing BGP filter generation. – Speakeasy
Routes must be registered with a recognised route registry: ARIN, RIPE or APNIC. – ATDN
Both parties are expected to register their routes in a public Internet Routing Registry (IRR) database, for the purposes of filtering. Both parties shall make good faith efforts to keep this information up to date. – nLayer All peers are expected to utilize IRR resources.
All peers will be configured with loose prefix limits based upon registered/announced routes to guard against leaks. Peers are encouraged to register routes or send notice in advance of dramatic deltas in announcements to allow for adjustments to those limits. -- RCN
# Peers should register and maintain proper route objects in the RADB or mirrored IRR. – Mzima
Routes must be registered with a recognized route registry: ARIN, RIPE or APNIC. – LambdaNet
Use of the Internet Routing Registry is encouraged. OpenAccess reserves the right to make entries into the IRR on behalf of the peer if needed. – OpenAccess
Each Peer will maintain accurate prefix and routing information in a publicly accessible Internet Routing Registry (IRR). – Highwinds
Must utilize RADB or mirrored IRR resources and shall be configured with max prefix limits, allowing 25% headroom, based upon registered/announced routes – Charter
Both parties are expected to register their routes in a public Internet Routing Registry (IRR) database, for the purposes of filtering. Both parties should make good faith efforts to keep this information up to date. – WVFiber
Mr Norton is Founder of DrPeering, an Internet Peering portal and consultancy, with over twenty years of Internet experience.
From 1998-2008, Mr. Norton’s title was Co-Founder and Chief Technical Liaison for Equinix. From the beginning, Mr. Norton focused on building a critical mass of carriers, ISPs and Content Providers. To this end, he created the white paper process, identifying interesting and important Internet peering operations topics, and documenting what he learned from the peering folks. He published and presented his research white papers in a variety of international operations and research forums. These activities helped establish the relationships necessary to atract the set of Tier 1 ISPs, Tier 2 ISPs, Cable Companies, and Content Providers necessary for a healthy Internet Exchange Point ecosystem.
DrPeering.net ©2014 | Privacy Policy | Terms and Conditions | About Us | Contact Us
The 2014 Internet Peering Playbook is now available on the iPad at the Apple Store and for the Amazon Kindle. The Kindle, ePub and PDF form are also perpetually updated on the DrPeering DropBox share.
